chore: explain status and proceedings of the DSP#255
Open
ssteinbuss wants to merge 1 commit intomainfrom
Open
Conversation
arnoweiss
reviewed
Mar 12, 2026
Contributor
arnoweiss
left a comment
There was a problem hiding this comment.
-I'd prefer to see this info in the top-level README.md but wouldn't block merging it to a new file like suggested. If that's decided, it should be properly linked in the top-level README.md.
juliapampus
requested changes
Mar 19, 2026
| ## Current Status | ||
| - The specification and supporting materials are in active development within this repository. | ||
| - The [release 2025-1](https://github.com/eclipse-dataspace-protocol-base/DataspaceProtocol/releases/tag/2025-1-err1) has been approved by the Eclipse Foundation and the Eclipse Dataspace Working Group. | ||
| - This release has been sent as PAS Submission to the ISO/IEC secretariat. An editorial review is conducted before the DIS ballot starts. (See the details of the procedure [here]() ) |
| - This release has been sent as PAS Submission to the ISO/IEC secretariat. An editorial review is conducted before the DIS ballot starts. (See the details of the procedure [here]() ) | ||
| - The Eclipse Dataspace Protocol team follows the common practice in ISO/IEC standardization to not work on documents while they are under ballot (stand-still). | ||
|
|
||
| ## Procedure to Be Followed |
Contributor
There was a problem hiding this comment.
I would move this section up, following the justification, and keep it abstract. Meaning: no check marks and add three steps/subprocesses before current step 1: GitHub release, Eclipse Foundation Release (incl. EDWG approval), submission to ISO. It must be clear that this process is to be followed for every "official modification" of the spec.
| 4. Submit the PAS package to ISO/IEC JTC via the Eclipse Foundation. (Done :white_check_mark:) | ||
| 5. Respond to any comments from ISO/IEC review and, if necessary, update the specification for publication. | ||
|
|
||
| ## Next Steps |
Contributor
There was a problem hiding this comment.
Could be merged with "current status" section.
| - **Industry alignment:** A PAS submission accelerates recognition of the specification as a stable, industry-ready baseline while allowing the community to retain control over the evolution of the specification. | ||
| - **Faster route to adoption:** The PAS route is designed to enable faster publication and uptake than a full international standard, which is important for technologies that require timely adoption. | ||
|
|
||
| ## Current Status |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR changes/adds
Add some status and next steps information on the standardization path
Why it does that
Stakeholder considerations
Linked Issue(s)
Closes #254
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.